home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
kermit.columbia.edu
/
kermit.columbia.edu.tar
/
kermit.columbia.edu
/
newsgroups
/
misc.20041116-20060924
/
000273_jaltman2@nyc.rr.com_Sun Mar 19 14:56:59 2006.msg
< prev
next >
Wrap
Internet Message Format
|
2006-09-27
|
3KB
Path: newsmaster.cc.columbia.edu!newsfeed.nyu.edu!newsfeed.cw.net!cw.net!news-FFM2.ecrc.de!news.glorb.com!cycny01.gnilink.net!cyclone1.gnilink.net!gnilink.net!news-feed-01.rdc-nyc.rr.com!news.rr.com!news-out.nyc.rr.com!news-wrt-01.rdc-nyc.rr.com.POSTED!53ab2750!not-for-mail
From: Jeffrey Altman <jaltman2@nyc.rr.com>
User-Agent: Thunderbird 1.5 (Windows/20051201)
MIME-Version: 1.0
Newsgroups: comp.protocols.kermit.misc
Subject: Re: closing a macro completely upon connect
References: <uGRPf.40748$VV4.591414@ursa-nb00s0.nbnet.nb.ca> <kLSPf.9392$X.1010@news-wrt-01.rdc-nyc.rr.com> <slrne10fck.8bc.fdc@sesame.cc.columbia.edu> <RqZPf.40942$VV4.594211@ursa-nb00s0.nbnet.nb.ca> <slrne10uul.jul.fdc@sesame.cc.columbia.edu> <H81Qf.41050$VV4.597519@ursa-nb00s0.nbnet.nb.ca> <ok2Qf.12766$nB6.1669@news-wrt-01.rdc-nyc.rr.com> <aQkQf.41491$VV4.608841@ursa-nb00s0.nbnet.nb.ca> <pVlQf.14280$4%1.10175@news-wrt-01.rdc-nyc.rr.com> <ATwQf.41716$VV4.616149@ursa-nb00s0.nbnet.nb.ca> <s3CQf.15925$nB6.6246@news-wrt-01.rdc-nyc.rr.com> <vmPQf.42198$VV4.628778@ursa-nb00s0.nbnet.nb.ca>
In-Reply-To: <vmPQf.42198$VV4.628778@ursa-nb00s0.nbnet.nb.ca>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Lines: 42
Message-ID: <3CVQf.10658$X.5797@news-wrt-01.rdc-nyc.rr.com>
Date: Sun, 12 Mar 2006 13:45:35 GMT
NNTP-Posting-Host: 68.175.91.105
X-Complaints-To: abuse@rr.com
X-Trace: news-wrt-01.rdc-nyc.rr.com 1142171135 68.175.91.105 (Sun, 12 Mar 2006 08:45:35 EST)
NNTP-Posting-Date: Sun, 12 Mar 2006 08:45:35 EST
Organization: Road Runner High Speed Online http://www.rr.com
Xref: newsmaster.cc.columbia.edu comp.protocols.kermit.misc:15524
Scott Caissie wrote:
> Compiled:
> Jeff's fix = corrects improper nesting with macro invocation.
> Frank's fix (when released) = is to activate of macro via connect mode. I
> had sent an email to him about this in the recent past. Middle of Janurary I
> think.
>
> Frank's bug and your fix sound similar enough that I thought they were
> related. They are, but indirectly. I can make due without the nesting fix. I
> just won't have a macro call another macro. I am still waiting for that
> other fix though.
The bugs are one and the same.
A macro mapped to a key will not execute if you enter CONNECT mode
directly. As described in the newbugs.txt file, if you want macros
to work from CONNECT mode then you must call CONNECT from within a prior
executing macro.
define doconnect {
echo Entering Connect Mode
CONNECT
echo Exiting Connect Mode
}
or
define doconnect {
CONNECT /SYNCHRONOUS
}
If you do not do this, then your macros won't execute and if you do
use this hack then you run into nesting problems.
If this is not what you want changed, then what you want is not a
bug fix. Macros executing from a key in CONNECT mode exit CONNECT
mode and return to COMMAND mode. This is working as designed. If
you would like a feature request to be implemented you can either
convince Columbia University to pay to have it developed or you can do
so yourself.
Jeffrey Altman